home *** CD-ROM | disk | FTP | other *** search
-
- This document contains the major changes between the 4.X and the
- 5.2 versions of the Installation Guide.
-
-
- Chapter 3 changes:
- ------------------
-
-
- 3.1 Enabling BOOTP Forwarding on Routers
-
- All routers (workstations or other devices with multiple network
- connections) between your workstation and a remote workstation that
- has the software distribution you plan to use must be modified to
- enable bootp forwarding. inst uses the Internet Bootstrap Protocol
- (BOOTP) to obtain IP addresses, but the default configuration of
- bootp(1M) in /usr/etc/inetd.conf prevents this.
-
- Step 1 below describes how to identify routers. Step 2 describes how
- to check to see if /usr/etc/inetd.conf has already been modified to
- enable bootp forwarding on Silicon Graphics workstations. Steps 3
- and 4 describe how to make the modifications on Silicon Graphics
- workstations. The procedure for making modifications to other types
- of routers may be different. You may want to ask a System Administrator
- or the owners of the routers to make the modifications for you.
-
-
- 1) Find out the names of the routers with the command:
-
- % /usr/etc/ping -R -c 1 <server>
-
- The ping output has a section that begins with RR:. It shows the
- route of a packet from your workstation to <server> and back to
- your workstation. Each of the workstations listed, other than
- <server> and your workstation, is a router.
-
-
- 2) Check the bootp line in /usr/etc/inetd.conf on each router. The
- bootp line in /usr/etc/inetd.conf looks like this by default:
-
- bootp dgram udp wait root /usr/etc/bootp bootp
-
- After the line has been changed (-f added), it should look like this:
-
- bootp dgram udp wait root /usr/etc/bootp bootp -f
-
-
- 3) If the file has not been changed, edit /usr/etc/inetd.conf '-f' as
- shown above. To simplify changing the file back to its original
- state, you may want to copy the original line, comment out one copy
- and change the other.
-
- 4) Give this command as superuser to make the change take effect:
-
- # /etc/killall -v -HUP inetd
-
-
- When the remote system is no longer needed for software installation,
- you can return the /usr/etc/inetd.conf file to its original state if
- desired and give the killall(1M) command again to make that change
- take effect.
-
-
-
- 3.2 Enabling TFTP Access on Remote Workstations
-
- The remote workstation that has the software distribution directory, tape
- drive, or CD-ROM drive you plan to use must be modified to allow tftp
- access. inst uses Trivial File Transfer Protocol (TFTP) in its transfer of
- files from remote workstations, but the default configuration of tftpd(1M)
- in /usr/etc/inetd.conf doesn't allow this transfer.
-
- Step 1 below describes how to check to see if /usr/etc/inetd.conf has already
- been modified to allow tftp access. Steps 2 through 5 describe how to make
- the modifications. You may want to ask a System Administrator or the
- owner of the remote workstation to make the modifications for you.
-
- 1) Check the tftp line in /usr/etc/inetd.conf on the remote
- workstation. The tftp line in /usr/etc/inetd.conf looks like
- this by default:
-
- tftp dgram udp wait guest /usr/etc/tftpd tftpd -s /usr/local/boot
-
- After the line has been changed (-s /usr/local/boot removed), it
- should look like this:
-
- tftp dgram udp wait guest /usr/etc/tftpd tftpd
-
- This change allows tftpd access to all publicly readable
- directories. The line might also have been modified as described
- in Step 3 and 4 below.
-
- 2) If the file has not been changed, edit /usr/etc/inetd.conf to
- remove "-s /usr/local/boot" as shown above. To simplify changing
- the file back to its original, secure state, you may want to copy
- the original line, comment out one copy and change the other.
-
- 3) If you want, you can limit remote access to just the distribution
- directory, CD-ROM distribution, or tape drive. Edit the tftp line
- in /usr/etc/inetd.conf again and add a directory at the end of
- the line as shown below. The first line below is for a distribution
- directory, the second line is for a CD-ROM distribution, and the
- third is for tape.
-
- tftp dgram udp wait guest /usr/etc/tftpd tftpd -s /usr/local/boot <distdir>
-
- tftp dgram udp wait guest /usr/etc/tftpd tftpd -s /usr/local/boot <CDdir>/dist
- tftp dgram udp wait guest /usr/etc/tftpd tftpd -s /usr/local/boot /dev
-
-
- 5) Give this command as superuser to make any changes to
- /usr/etc/inetd.conf take effect:
-
- # /etc/killall -v -HUP inetd
-
- When the remote system is no longer needed for software installation,
- you can return the /usr/etc/inetd.conf file to its original state if
- desired and give the killall(1M) command again to make that change
- take effect.
-
-
-
- 3.3 Configuring an Installation User ID
-
- When you are doing an installation from a remote distribution source,inst
- uses the user ID guest (with no password) on the remote workstation by
- default. If a guest user ID without a password is available on the remote
- workstation, then that user ID can be used without modification.
-
- If no guest account exists on the remote workstation or the guest account
- has a password (typically this would be done to limit access to the remote
- workstation by rsh), you must provide an alternate means for inst to access
- the remote workstation. There are three alternatives:
-
- o Remove the password from guest while installations are taking place.
-
- o Use a different user ID on the remote workstation that does not
- have a password. This user ID is specified with the inst ¡f flag
-
- o Use a user ID with a password on the remote workstation and special
- entries in its .rhosts file on the remote workstation. An entry
- needs to be made for each workstation that uses the remote
- workstation for installation. Each entry contains the name of
- the local workstation and the name of the user ID to be used on
- the remote workstation. For example, the file
- /usr/people/instuser/.rhosts on the workstation "bigserver" might
- contain the lines:
-
- joesbox.engr.xxx.com instuser
- lab1.engr.xxx.com instuser
-
- When installing new software on "joesbox" or "lab1", you would
- give one of these two commands, depending on the circumstances:
-
- # /usr/sbin/inst -f instuser@bigserver:<path>
-
- Inst> from instuser@bigserver:<path>
-
- where <path> is the device or directory that has the software
- distribution. Sections 7.5 and 10.2 describe inst ¡f and from,
- respectively. /usr/people/instuser/.rhosts must have the correct
- owner and permissions for this to work. See the hosts.equiv(4)
- manual page for details.
-
- No matter what user ID you choose, it must have read permission for the
- software distribution source (the tape drive, the directory where the
- CD-ROM drive is mounted, or the distribution directory).
-
-
-
-
- Chapter 7 changes / Prom Chart:
- ------------------
-
- Table 7-1 Miniroot Installation Procedures:
- Remote
- Local Local Remote Remote Distribution
- <cpu> Tape CD-ROM Tape CD-ROM Directory
- --------------------------------------------------------------------
- IP4 A N/A F H J
- IP5, IP6, IP7, IP9 A C F H J
- IP12, IP17 A D F H J
- IP19, IP20, IP22 B E G I K
- --------------------------------------------------------------------
-
-
-
- Table 7-2 Command Monitor Commands to Load the Miniroot:
-
- Procedure Commands
- --------------------------------------------------------------------
- A >> setenv tapedevice <device>(<cntlr>,<unit>)
- >> boot -f $tapedevice(sash.<cpu>) --m
-
- B >> setenv tapedevice <device>(<cntlr>,<unit>)
- >> boot -f $tapedevice(sashARCS) --m
-
- C >> dksc(<cntlr>,<unit>,8)sash.<cpu> -m
-
- D >> dksc(<cntlr>,<unit>,8)sash<cpu> -m
-
- E >> dksc(<cntlr>,<unit>,8)sashARCS -m
-
- F >> setenv tapedevice bootp()<server>:<tapedevice>
- >> boot -f $tapedevice(sash.<cpu>) --m
-
- G >> setenv tapedevice bootp()<server>:<tapedevice>
- >> boot -f $tapedevice(sashARCS) --m
-
- H >> setenv tapedevice bootp()<server>:<CDdir>/dist/sa
- >> boot -f $tapedevice(sash.<cpu>) --m
-
- I >> setenv tapedevice bootp()<server>:<CDdir>/dist/sa
- >> boot -f $tapedevice(sashARCS) --m
-
- J >> setenv tapedevice bootp()<server>:<distdir>/sa
- >> boot -f $tapedevice(sash.<cpu>) --m
-
- K >> setenv tapedevice bootp()<server>:<distdir>/sa
- >> boot -f $tapedevice(sashARCS) --m
- --------------------------------------------------------------------
-
-
-
-
-
- Chapter 8 changes:
- ------------------
-
- 8.2.2 Checking Network Connections
-
- The steps below explain several tests and checks that you can perform to
- verify your workstations connection to a remote workstation.
-
- 1) Test the TCP/IP connection from IRIX.
-
- If IRIX is running on your workstation, do a simple check of the
- network connection with this command:
-
- % /usr/bsd/rsh <server> -l <user> date
-
- where <server> is the name of the remote workstation and <user>
- is the user ID you are using for installation. Normally, <user>
- is "guest". If the date isn't returned, you've specified the wrong
- <server>, there is a network problem, or <user> isn't a valid user
- ID.
-
- 2) Test the TCP/IP connection from inst.
-
- Connections to remote workstations are done over terminal control
- program/internet protocol (TCP/IP) in a manner similar to rsh(1C).
- A simple test of this connection can be done while you are doing
- an IRIX Installation by escaping to a shell from any inst prompt
- and using ping(1M):
-
- Inst> sh
-
- # /usr/etc/ping -q -f -s 2048 -c 100 <server>
- PING <server> (<IPaddress>): 2048 data bytes
-
- ----<server> PING Statistics----
-
- 100 packets transmitted, 100 packets received, 0% packet loss
- round-trip (ms) min/avg/max = 0/2/7
- # exit
- Inst>
-
- where <server> is the name of the remote workstation. If you see
- packet loss, you could have a problem with your network connection.
-
- This network connection test is not possible if you are using
- Miniroot Installation; if you are, test the connection before
- beginning the installation if possible. Use the same ping
- command as in the example above while in an IRIX shell.
-
- 3) Check the setting of the netaddr NVRAM variable.
-
- In some situations, you might have network problems if the IP
- address (<localIPaddress>) of your workstation in its non-volatile
- random access memory (NVRAM) doesn't match its IP address in
- /etc/hosts. A mismatch can occur when you move a workstation, but
- not cause a problem until you attempt to load the miniroot for a
- software installation. You can check the IP address in the NVRAM
- on your workstation while you are using IRIX, or when you have
- escaped to the shell while using inst by giving this command:
-
- % /etc/nvram netaddr
-
- From the Command Monitor, you can check IP address in the NVRAM
- with this command:
-
- >> printenv netaddr
-
- If the four part number returned from either command doesn't match
- the IP address in /etc/hosts on your workstation (the value of
- <localIPaddress> that you noted while bringing up inst), change
- it with one of these two commands (not all models of workstations
- support changing NVRAM from IRIX):
-
- # /etc/nvram netaddr <localIPaddress>
-
- >> setenv netaddr <localIPaddress>
-
- 4) Verify that the remote workstation allows tftpd(1M) access.
-
- See above section on "Enabling TFTP Access on Remote Workstations",
- describes the procedure for verifying that the remote workstation
- has been modified to allow tftp access.
-
- To get more debugging information, add the ¡l option to the tftp
- line in /usr/etc/inetd.conf and restart inetd(1M). The line should
- look like this:
-
- tftp dgram udp wait guest /usr/etc/tftpd tftpd -l
-
- Debugging information is written to /usr/adm/SYSLOG.
-
- 5) Verify that routers between your workstation and the remote
- workstation forward bootp(1M) packets.
-
- See above section on "Enabling BOOTP Forwarding on Routers",
- describes the procedure for verifying that routers have been
- modified to allow bootp access.
-
- To get more debugging informatio, add the -d option on the bootp
- line in /usr/etc/initd.conf and restart initd(1M). The line should
- look like this:
-
- bootp dgram udp wait root /usr/etc/bootp bootp -f -d
-
- Debugging information is written to /usr/adm/SYSLOG.
-
- For more information on networking, see the IRIX Advanced Site and
- Server Administration Guide and the NFS and NIS Administration Guide
- and Man Pages.
-
-
- 8.2.5 Checking CD-ROM Drives
-
- To check CD-ROM drives, you must verify that:
-
- o The system recognizes the CD-ROM drive.
-
- o The CD you want to use is mounted.
-
- The sections below explain the procedures.
-
- Verifying That a CD-ROM Drive is Recognized
-
- The procedure to verify that a CD-ROM drive is recognized depends
- on your situation:
-
- o If IRIX is running, give the hinv command:
-
- % hinv
-
- For each CD-ROM drive, you should see one line of output. For
- example:
-
- CDROM: unit 4 on SCSI controller 0
-
- If you do not see a line of output for a CD-ROM drive, it is not
- recognized.
-
- o If you are in the miniroot, escape to a shell with the shroot
- command (see Section 7.20), and give the hinv command:
-
- # hinv
-
- For each CD-ROM drive, you should see one line of output. For
- example:
-
- CDROM: unit 4 on SCSI controller 0
-
- If you do not see a line of output for a CD-ROM drive, it is not
- recognized.
-
- o If you are in the Command Monitor, give the hinv command:
-
- >> hinv
-
- For each CD-ROM drive, you should see one line of output. Some
- examples are:
-
- SCSI CDROM: dksc(0,4)
- SCSI CDROM: scsi(0)cdrom(4)
- SCSI Disk: dksc(0,4)
-
- The last example shows the CD-ROM drive on an older workstation.
- The CD-ROM drive is recognized, but it is shown as a disk. If you
- do not see a line of output for a CD-ROM drive, it is not recognized.
-
- When a CD-ROM drive is not recognized, it usually because the CD-ROM
- drive was not powered up properly. If it is an external drive, the
- CD-ROM drive must be powered on before the workstation main unit is
- powered on.
-
- The procedure for making the system recognize the CD-ROM drive depends
- on whether you are running IRIX or the miniroot:
-
- o If you are running IRIX, exit inst if it is running, warn other
- users, shut the workstation down with shutdown(1M) or use System
- Shutdown on the System menu, then reboot the workstation to bring
- up IRIX again.
-
- o If you are in the miniroot, get back to the PROM Monitor, press the
- Reset button on the workstation main unit, and then bring up inst
- again. If this doesn't fix the problem, turn the CD-ROM drive off
- and then on again.
-
-
- Verifying That a CD is Mounted
-
- When using a CD-ROM drive, the CD that contains the software you want
- to install must be mounted. Mounting is done automatically by inst when
- using a local CD-ROM. When using a remote CD-ROM, the mounting is
- done by the command cdinstmgr(1). To verify that the CD is mounted,
- use the df(1) command below. If you are using local CD-ROM, escape to
- a shell. If you are using a remote CD-ROM, give the command on the
- remote workstation.
-
- % /bin/df
-
- Look at the directory names on the right. For local CD-ROM, you should
- see /CDROM. For remote CD-ROM, the name /CDROM is likely, but another
- directory name for the mount point, <CDdir>, may have been chosen.
-
- If the CD is mounted, list the files it contains using in order to
- verify that you have the correct CD inserted. If the CD is not mounted
- and you are using a remote workstation, verify that cdinstmgr is
- running. If it isn't, start it.
-
- To verify that a distribution directory or a mounted CD contains
- the right files, the workstation that contains the distribution must
- be running IRIX. Change directories to the directory (<distdir> or
- <CDdir>/dist) and list the files with ls(1). Files in software
- distributions have these names:
-
- mr
- sa
- <product>
- <product>.idb
- <product>.<image>
- ...
-
-